Author Topic: Features Wishlist (Read 702839 times)

DJ Omnimaga · « **Reply #1260 on:** September 25, 2010, 10:46:19 pm »

I changed my vote because after seeing LordConiputer entry and having many others at once on my calc, and having used the CATALOG for a while, I feel that it might be better to have the list so when you type a letter, it goes to the first program that has that letter.

DJ Omnimaga · « **Reply #1261 on:** September 27, 2010, 09:40:28 pm »

After compiling, I still think it would be nice, when compiling in program form, if Axe let us know how large is our executable code after compiling, so it give us a guide if we want to know if we are nearing the 8812 bytes limit and are trying to stay under it.

Quigibo · « **Reply #1262 on:** September 27, 2010, 09:59:38 pm »

The main problem with that is the compiler doesn't know how big the output file is until it finishes compiling. It would have to pause when its done somehow to allow the user to see the number which I think would annoy a lot of people who want speedy fast compiling, especially for smaller programs.

Michael_Lee · « **Reply #1263 on:** September 27, 2010, 10:01:32 pm »

Maybe add an option that'll let you enable that?

DJ Omnimaga · « **Reply #1264 on:** September 27, 2010, 10:38:00 pm »

Ah ok I see

How are you gonna add a warning that the code exceeds 8812 bytes, though? If it is possible to do, then why at the end of the compiling wouldn't it be possible to tell a size other than 8812?

Quigibo · « **Reply #1265 on:** September 27, 2010, 11:41:10 pm »

I'm not saying its impossible, I just mean that it would be annoying to happen every time you compile a program. You definitely need to know when you're over the limit because that's a safety issue (potential crashes), but for smaller programs its not important since you cn check in the [2nd][Mem] menu anyway.

I like the idea of an option for it though. I could display other statistics too like the number Axe subroutines used, percent data, tip of the day, etc.

DJ Omnimaga · « **Reply #1266 on:** September 27, 2010, 11:50:08 pm »

would it absolutely slow down compiling, though? I thought it would simply be a matter of scanning through the file until the point where is located the data, then display the size, like when you compile an APP (although that displays the size including data).

If it's really inconvenient for smaller programs, I guess maybe it could be at least added as option, though.

Raylin · « **Reply #1267 on:** September 28, 2010, 12:21:38 am »

It would be best to make a separate option [in OPTIONS] called 'Generate Report' that CALLS the compiler routine and but doesn't show the compile percentages. (The first pass and second pass thing.) Instead, it would say "Generating report..." and then display:

*Name of program:
*Bytes when compiled and warning if necessary
*Number of subroutines
*Composition percentile (how much is data, etc.)
*Tip of the day / "Did you know"

That's just my idea.

LordConiupiter · « **Reply #1268 on:** September 28, 2010, 11:19:01 am »

I like that idea! and I would name the option Compile in the OPTIONS menu, which could be set to report or percentage, and perhaps also both?

DJ Omnimaga · « **Reply #1269 on:** September 28, 2010, 11:40:32 am »

Quote from: Raylin on September 28, 2010, 12:21:38 am

It would be best to make a separate option [in OPTIONS] called 'Generate Report' that CALLS the compiler routine and but doesn't show the compile percentages. (The first pass and second pass thing.) Instead, it would say "Generating report..." and then display:

*Name of program:
*Bytes when compiled and warning if necessary
*Number of subroutines
*Composition percentile (how much is data, etc.)
*Tip of the day / "Did you know"

That's just my idea.

that could work too

Raylin · « **Reply #1270 on:** September 28, 2010, 11:42:08 am »

I'd make it a separate option entirely. Compile seems too ambiguous.

DJ Omnimaga · « **Reply #1271 on:** September 28, 2010, 11:57:32 am »

Yeah, and maybe I guess it is better if compiling is not too slow either. I tried contest entries and I know that some took quite a while to compile, and I was on a 15 MHz calc. NOw imagine on a regular 83+.

Raylin · « **Reply #1272 on:** September 28, 2010, 11:59:14 am »

DJ, you run on a 15MHz? Which one?
And, I agree. Compiling needs to be fast.

Still voting for the compile keyhook inside of a program.

DJ Omnimaga · « **Reply #1273 on:** September 28, 2010, 12:03:24 pm »

I usually run on my 83+. However, I slowly moved to my TI-Nspire because APP compiling doesn't work on my TI-83 Plus (hardware issue, I think).

Raylin · « **Reply #1274 on:** September 28, 2010, 12:08:33 pm »

Awh... That sucks... :c
Isn't the Nspire slow and suckish for ASM? Or was that BASIC...?

Author Topic: Features Wishlist (Read 702839 times)

DJ Omnimaga

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

Quigibo

Re: Features Wishlist

Michael_Lee

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

Quigibo

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

Raylin

Re: Features Wishlist

LordConiupiter

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

Raylin

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

Raylin

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

Raylin

Re: Features Wishlist