[Misc-Scripts] Touchscreen Right-Click | File System Iterator | File Hex Dump | Vigenere Cipher

A few tips for your code:

• Instead of if not startPath then startPath = "/" end consider startPath = startPath or "/"
• fs.combine handles trailing/leading slash problems
• There are nicer ways to write iterators in lua than passing in a table and having your code populate it. Check out PIL 7 and 9.3.

With these changes applied:

local function yieldFileSystem(startPath, ignorePaths, debug)
	startPath = startPath or "/"
	ignorePaths = ignorePaths or {}
	local fsList = fs.list(startPath)
	for _, file in ipairs(fsList) do
		local path = fs.combine(startPath, file)
		if not contains(ignorePaths, path) then
			if fs.isDir(path) then
				yieldFileSystem(path, ignorePaths, debug)
			else
				coroutine.yield(path, file)
			end
		else
			if debug then print("Ignoring: "..path) end
		end
	end
end

function fileSystemIter(startPath, ignorePaths, debug)
	startPath = startPath or "/"
	ignorePaths = ignorePaths or {}
	return coroutine.wrap(function()
		yieldFileSystem(startPath, ignorePaths, debug)
	end)
end

Which can then be used as:

for fullPath, filename in fileSystemIter("/", { "/rom", ".git" }) do
	print(fullPath, filename)
end

Eric, on 14 January 2013 - 09:15 AM said:

A few tips for your code:

• Instead of if not startPath then startPath = "/" end consider startPath = startPath or "/"
• fs.combine handles trailing/leading slash problems
• There are nicer ways to write iterators in lua than passing in a table and having your code populate it. Check out PIL 7 and 9.3.

Thanx for the fixes… I threw this together at about 3am… so was gunna fix up any coding mistakes from being tired when I woke up this morning…

Using the table population over an iterator was a coding choice I made late last night, because of these reasons:

1. I was allowing for ease of use on the end where people actually use it
2. Even though we know how to use iterators does not mean everyone does, it seems quite a few of the people that are writing the popular OSes and programs that would use this, are fairly new to programming and only know the basics (including only the basics of tables)
3. Having a table they don't have to iterate the file system each time they wanted to do something

Continuing on the third point, they could then just access the table and stop when they have found what they are looking for, instead of having a recursive function that has to run to the end and they cant stop it. Granted they could initially iterate and instead of printing the value store it in a table, the just do the intended outcome from that table…. but I didn't think of that until now :P/>

Lastly, did you actually run that solution you made before trying to push it to my git? if you did you would notice that it actually still iterates the ignore paths if its in the root directory for example if I enter "/rom" it WILL iterate rom (and it shouldn't), if I enter "rom" it won't iterate rom… not using fs.combine was a coding choice that allowed it to work EITHER way the user input it… granted it now occurs to me that i could have just used "/"..fs.combine but thats not the point I'm making here :P/>

Again thanx for the fix though :)/>

TheOriginalBIT, on 14 January 2013 - 10:59 AM said:

Thanx for the fixes… I threw this together at about 3am… so was gunna fix up any coding mistakes from being tired when I woke up this morning…

Using the table population over an iterator was a coding choice I made late last night, because of these reasons:

1. I was allowing for ease of use on the end where people actually use it
2. Even though we know how to use iterators does not mean everyone does, it seems quite a few of the people that are writing the popular OSes and programs that would use this, are fairly new to programming and only know the basics (including only the basics of tables)
3. Having a table they don't have to iterate the file system each time they wanted to do something

Ok, I hadn't considered those things.

TheOriginalBIT, on 14 January 2013 - 10:59 AM said:

Continuing on the third point, they could then just access the table and stop when they have found what they are looking for, instead of having a recursive function that has to run to the end and they cant stop it. Granted they could initially iterate and instead of printing the value store it in a table, the just do the intended outcome from that table…. but I didn't think of that until now

But that accesses the entire filesystem first! If you break out of the for loop with my iterator, the entire thing stops working.

TheOriginalBIT, on 14 January 2013 - 10:59 AM said:

Lastly, did you actually run that solution you made before trying to push it to my git? if you did you would notice that it actually still iterates the ignore paths if its in the root directory for example if I enter "/rom" it WILL iterate rom (and it shouldn't), if I enter "rom" it won't iterate rom… not using fs.combine was a coding choice that allowed it to work EITHER way the user input it… granted it now occurs to me that i could have just used "/"..fs.combine but thats not the point I'm making here :P/>

Running things is hard :P/>. My bad.

Eric, on 14 January 2013 - 11:26 AM said:

Ok, I hadn't considered those things.

I might post up both versions so they can choose… :)/>

Eric, on 14 January 2013 - 11:26 AM said:

But that accesses the entire filesystem first!

Which isn't really much, like I said in OP I have 852 files in my file system and its done in less than a second…

Eric, on 14 January 2013 - 11:26 AM said:

If you break out of the for loop with my iterator, the entire thing stops working.

Thats my point, you break from an iterator and it stops working… break from a loop iteration (while searching for a particular path) and it doesn't stop anything from working… minor details though…

Eric, on 14 January 2013 - 11:26 AM said:

Running things is hard :P/>. My bad.

Haha thats ok



EDIT: Oh and also the reason I used

if debug == true then

was also a coding choice at the time so that it will ONLY debug when the param is true, not when its accidental and might be "/rom" because they put an ignore in the wrong place… :)/>

In the Touchscreen Right Click part it says:

pastebin LkfDRrAt touch

instead of:

pastebin get LkfDRrAt touch

XP

MudkipTheEpic, on 16 January 2013 - 03:11 PM said:

-snip-

Thanx for picking up on my typo :)/>

encodeString

Decodes a string?

LOLWHAT! CopyPasta fail, T.O-BIT

NeverCast, on 22 January 2013 - 07:36 PM said:

encodeString

Decodes a string?

LOLWHAT! CopyPasta fail, T.O-BIT

Yeh its was late when i did that… never even noticed it… fixed… thanx

You're welcome :)/>
Nice work btw, Just been reading about the algorithm, which paved it's way to a frequency analysis topic.. I wonder if that has a place in CC xD

NeverCast, on 22 January 2013 - 07:41 PM said:

You're welcome :)/>
Nice work btw, Just been reading about the algorithm, which paved it's way to a frequency analysis topic.. I wonder if that has a place in CC xD

Thanx :)/> Yeh its was an interesting topic when we did it at uni…. there is a major flaw to the cypher tho, when encoding a 'Z' with any key char or encoding any char with a 'Z' in the key, the output is no different… its since been shifted a little to not have that happen, however we had to implement the original one ( made it easier to debug ) so thats what I did for this one… We actually had to implement the frequency analysis that was outlined on the wikipedia page… but i saw little point to that one… why would I post a way to crack the cypher on the same post as the cypher. :P/>

actually on second thought it was the shifted one that had the Z flaw… it was the original that had the flaw of encoding a letter with the same letter, yielded no change… yeh that sounds better :P/>

Locked by request.