Working towards a release

[MCMic]

Meh, my plan was to remove the email address of the post with the edit function, could you remove your quote?

Levelpack incomming.

[Edward_Lii]

Hello MCMic,

Meh, my plan was to remove the email address of the post with the edit function, could you remove your quote?

Done.

Levelpack incomming.

Can't wait.

[MCMic]

Somehow the "update level names" feature does not work.
I created the levelpack, then I updated the levels adding level names, then I used it on my levelpack and saved it, still no names in the interface.

I'll try removing and re-adding levels.

[Edward_Lii]

Hello MCMic,

Somehow the "update level names" feature does not work.
I created the levelpack, then I updated the levels adding level names, then I used it on my levelpack and saved it, still no names in the interface.

Levelpacks contain their own levels, when composing a levelpack the levels will be moved.
When altering the original level the "copied" levels in the levelpack don't change.

I'll try removing and re-adding levels.

Currently that's the only way to solve it.

[MCMic]

It worked.
I just understood creating a levelpack make a copy of levels. I'm not sure that's a good idea.
Please find my level pack attached. (Supposed to be challenging on the last 3 levels)
I think there is an interface design error : we can't see if we succeed the last level. Won levels and accessible levels are drown the same way.

[Edward_Lii]

Hello MCMic,

Please find my level pack attached. (Supposed to be challenging on the last 3 levels)

Wow, I've played trough the levels and mus say it requires some skills.
But nevertheless fun to play, did you now that you that in the level move after you've used the switch you can reach the exit by quickly moving over the moving blocks and finish without the help of your shadow.

Should I add this levelpack to the addons?

I think there is an interface design error : we can't see if we succeed the last level. Won levels and accessible levels are drown the same way.

Kinda true, perhaps we should leave that for 0.3 (in which statistics) are planned.
Let's try doing some final things -> enter some sort of feature freeze -> release candidate -> 0.2.

We should make a roadmap and try to get one big feature per release.
Then try to get the desired release early, release often.

What do you think?

[MCMic]

I did know we could jump on the moving block but I thought we could not go to the end without the shadow. I'll need to fix this.

I think 0.2 should have been out for some time now, you spent too much time reading what I write and coding what I ask and not enough tagging svn and uploading release candidates :-P

[Edward_Lii]

Hello MCMic,

I did know we could jump on the moving block but I thought we could not go to the end without the shadow. I'll need to fix this.

It was quite hard to do, but after ~20 go's I made it.

think 0.2 should have been out for some time now, you spent too much time reading what I write and coding what I ask and not enough tagging svn and uploading release candidates :-P

Let's call it a feature freeze then.
Now I'll try to get a release candidate out.

Are there any small improvements that need to be done before the release candidate?

[MCMic]

Development is all about small elements. I'd say review the order of level element in the map editor would be a good idea. (Come on, block and shadow block are not one mousewheel appart?)

[Edward_Lii]

Hello MCMic,

Development is all about small elements. I'd say review the order of level element in the map editor would be a good idea. (Come on, block and shadow block are not one mousewheel appart?)

IMHO development is mostly about getting it working.
After that you can focus on improving and polishing.

About the order, currently it's the order of the type id's.
What order were you thinking?

Normal->Shadow->Spikes->Player start->Shadow start->Exit
Fragile->Normal moving->shadow moving->Moving spikes
Conveyor belt->Shadow conveyor belt
Button->Switch->Portal->Swap->Checkpoint->Notification block

[MCMic]

Yeah, something like that seems better.
I'd move the player starts and exit to the end. (they'll be available by cycling backward)

[Edward_Lii]

MeAndMyShadow V0.2 Release Candidate 1

Levelpacks: default, tutorial, classic
Themes: classic, Cloudscape (Waiting for Tedium)
Levels: None? (Perhaps yours MCMic?)

Download:

* Source: (Still to come)
* Linux: (Still to come)
* Windows: (Still to come)

Found bugs:


Feedback is welcome!

[MCMic]

There should not be any levels outside of levelpacks imho

[Edward_Lii]

Hello MCMic,

There should not be any levels outside of levelpacks imho

Yes and no,
Imagine a new user who made a level and wants to share it.
He would have to wrap it into a levelpack in order for others to play it.

Or did you mean in the release candidate and in the release?

[KroArtem]

I think he means in the release candidate and in the release. I'm feeling guilty but I didn't have time to make some levels for me&myshadow :/

[Edward_Lii]

Hello KroArtem,

I think he means in the release candidate and in the release. I'm feeling guilty but I didn't have time to make some levels for me&myshadow :/

Don't feel guilty, we're all doing it in our spare time.
And you've already helped a lot.

BTW, you can still make some levels.
They can always be put in the addon manager.

[acme_pjz]

Hi,

Are there any small improvements that need to be done before the release candidate?

IMHO add level properties and level pack editor to the the level editor's tool bar; and add tool tip text to the tool bar

And Ctrl+E in normal playing doesn't work properly; should we remove this feature?

[Edward_Lii]

Hello acme_pjz,

IMHO add level properties and level pack editor to the the level editor's tool bar; and add tool tip text to the tool bar
And Ctrl+E in normal playing doesn't work properly; should we remove this feature?

I'll try to do this and then release the release candidate.

[KroArtem]

I'd say you should remove forum support from sourceforge page (or to redirect it here) and to update information/description/screenshots on SF page.

P.S. Btw, I've edited 2 pages and added a short instruction about how to compile under linux. Not sure the formatting is ok, please check whether everything is done properly

[Edward_Lii]

Hello KroArtem,

I'd say you should remove forum support from sourceforge page (or to redirect it here) and to update information/description/screenshots on SF page.

Done,

P.S. Btw, I've edited 2 pages and added a short instruction about how to compile under linux. Not sure the formatting is ok, please check whether everything is done properly

Thanks.
It looks alright, only one thing cmake . does produce a CMakeCache file but the main goal is making a Makefile which make can use.

[MCMic]

For the levelpack editor icon, you should use the level properties icon multiple time instead of the save icon multiple times, it makes more sense.

[EDIT] Classic level pack needs an other definition, "default level pack" is confusing with the actual default level pack.

[Edward_Lii]

Hello MCMic,

For the levelpack editor icon, you should use the level properties icon multiple time instead of the save icon multiple times, it makes more sense.

Your right, that does make more sense, currently it looks like some sort of "Save All" icon.
Added to the TODO list: http://meandmyshadow.sourceforge.net/wiki/index.php/TODO

[MCMic]

I'm not sure it's a good idea to have a todo page and a roadmap page. I only edit the roadmap one…

[Edward_Lii]

Hello MCMic,

I'm not sure it's a good idea to have a todo page and a roadmap page. I only edit the roadmap one…

I though we could use the Roadmap page for planning ahead and only writing "large" things.
The TODO list more for every task before the next release, STK does it that way AFAIK.

But perhaps you're right, having it all in one place is better.

Another idea for the long-term could be multiple resolutions and/or openGL support (using SDL).

[acme_pjz]

Hi,

The TODO list more for every task before the next release

I prefer bug/issue tracker