John said before that Lupo's menu is just Asuite. Or is that somebody else?
Anyway, Asuite has a skin or something that looks like the PortableApps.com Platform. I think it's a skin. If you look up Asuite and you look at their screenshots, one looks like the PA.c Platform (kinda) and the other looks completely different. So I guess it's a skin/theme.
I'm not a PortableApps.com's member, but I'm only an user.
yeah, asuite has two modes. something that looks like pstart and something that looks like pam.
Right. ASuite has two menus:
- Classic Menu (see img)
- Graphic Menu (XP/Vista style) (see img)
Asuite has a skin or something that looks like the PortableApps.com Platform.
Yes...For this "issue", I can't promote any new version of ASuite in this forum.
Under the policy, forks and clones are not permitted to be self-promoted. The themable look of ASuite was originally using code from the PortableApps.com Platform. To his credit, El Salvador did then rewrite the code to try to be able to post here again when the policy was pointed out to him.
Even with the rewrite, though, it was still a near-pixel-perfect duplicate of the theme setup and menu layout we created. Many people mistake it for a fork or clone of the PA.c Menu on first look as the layout and elements are the same (with the exception of the most recent apps lower section). But it is not a fork. It's original code written by El Salvador and based on a different concept (more manual control, less automation, no PA.c Format integration, etc).
As we're now centered around PortableApps.com Format and the PortableApps.com Platform, other menus aren't appropriate for self-promotion here any longer, unless they serve as an add-on and are in PA.c Format. Promoting multiple menus with multiple ways of interacting with apps is a bit counter-intuitive to our goals, though we strive to have our apps be menu-agnostic.
Just because ASuite is used by projects which routinely violate the GPL and trademark law and/or have stolen code from us (Liberkey, Lupo, etc) doesn't mean El Salvador is in any way connected with them.
This is quite off-topic from the original post, so I think we should either stay on topic or let the topic die (and lock it).
Sometimes, the impossible can become possible, if you're awesome!
I encourage everyone to take a look at This thread.
solanus
I agree that Lupo should have credited the original developers, and he (she?) is a snake, but where are OUR guys?
If it is such a valuable tool, and we are so protective of it, why has it languished in soon-to-be-renamed, beta-5b-development limbo for 19 months?
solanus, I completely agree, and I apologize to the community for letting the project sit idle for so long. I addressed this issue in detail in the above post, but I think this comment is the best description of the issue I have caused. Please accept my humble apologies.
This was so not meant as a poke at you specifically! No apologies necessary.
I read your post, and I wish you all the best at school.
It's just a current weakness of the system here, that apps generally don't have a clear succession plan.
However...
Our devs have TOTALLY stepped up and are raging forward with this app!
You gotta love it!
I made this half-pony, half-monkey monster to please you.
I didn't interpret it as a poke at me - sorry to single your comment out - I'm just recognizing the fact that I *knew* that I would not be able to continue to support eXpresso a lot earlier that now, and I probably *could have* made a post and kick started development on it again, a lot earlier and before the whole Lupo thing happened. I just feel that since I was the dev for that particular app (that happens to be important to the community) that I have some responsibilities that I didn't live up to.
Although, if Lupo was going to rip it off, it was going to happen regardless of the release status, so I guess that one was beyond my control. It's disappointing though.
Is this thread still going? Let it die people! Leave "loophole" to his (or her) devices.
Listen, and understand. That loophole is out there. He(she) can't be bargained with. He can't be reasoned with. He doesn't feel pity, or remorse, or fear. And he absolutely will not stop, ever, until PA.c is dead.
Looks like some people can't get over how good this site has gotten and are jealous that they can't develop their own crap. This is sad. Really. :|
Na na na, come on!
:/
You actually post for once!!!
For a moment there, I thought he became addicted to Spanish and Portugese...
Insert original signature here with Greasemonkey Script.
Can we stay on topic for once?
Na na na, come on!
..that his menu looks eerily similar to PA.c?
!!
They are jealous of PortableApps.com's abilities and can't manage to do it on their own.
Na na na, come on!
John said before that Lupo's menu is just Asuite. Or is that somebody else?
Anyway, Asuite has a skin or something that looks like the PortableApps.com Platform. I think it's a skin. If you look up Asuite and you look at their screenshots, one looks like the PA.c Platform (kinda) and the other looks completely different. So I guess it's a skin/theme.
yeah, asuite has two modes. something that looks like pstart and something that looks like pam.
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world
Actually, ASuite was created by one of PortableApps.com's Members.
https://portableapps.com/node/5765
I'm not a PortableApps.com's member, but I'm only an user.
yeah, asuite has two modes. something that looks like pstart and something that looks like pam.
Right. ASuite has two menus:
- Classic Menu (see img)
- Graphic Menu (XP/Vista style) (see img)
Asuite has a skin or something that looks like the PortableApps.com Platform.
Yes...For this "issue", I can't promote any new version of ASuite in this forum.
Why? Just because it LOOKs like PAP doesn't mean you can't post it here. Your apps Open Source too so it's not self-promotion.
I think John told him not to... here.
Insert original signature here with Greasemonkey Script.
Oh, thanks.
Under the policy, forks and clones are not permitted to be self-promoted. The themable look of ASuite was originally using code from the PortableApps.com Platform. To his credit, El Salvador did then rewrite the code to try to be able to post here again when the policy was pointed out to him.
Even with the rewrite, though, it was still a near-pixel-perfect duplicate of the theme setup and menu layout we created. Many people mistake it for a fork or clone of the PA.c Menu on first look as the layout and elements are the same (with the exception of the most recent apps lower section). But it is not a fork. It's original code written by El Salvador and based on a different concept (more manual control, less automation, no PA.c Format integration, etc).
As we're now centered around PortableApps.com Format and the PortableApps.com Platform, other menus aren't appropriate for self-promotion here any longer, unless they serve as an add-on and are in PA.c Format. Promoting multiple menus with multiple ways of interacting with apps is a bit counter-intuitive to our goals, though we strive to have our apps be menu-agnostic.
Just because ASuite is used by projects which routinely violate the GPL and trademark law and/or have stolen code from us (Liberkey, Lupo, etc) doesn't mean El Salvador is in any way connected with them.
This is quite off-topic from the original post, so I think we should either stay on topic or let the topic die (and lock it).
Sometimes, the impossible can become possible, if you're awesome!
I encourage everyone to take a look at This thread.
solanus, I completely agree, and I apologize to the community for letting the project sit idle for so long. I addressed this issue in detail in the above post, but I think this comment is the best description of the issue I have caused. Please accept my humble apologies.
This was so not meant as a poke at you specifically! No apologies necessary.
I read your post, and I wish you all the best at school.
It's just a current weakness of the system here, that apps generally don't have a clear succession plan.
However...
Our devs have TOTALLY stepped up and are raging forward with this app!
You gotta love it!
I made this half-pony, half-monkey monster to please you.
I didn't interpret it as a poke at me - sorry to single your comment out - I'm just recognizing the fact that I *knew* that I would not be able to continue to support eXpresso a lot earlier that now, and I probably *could have* made a post and kick started development on it again, a lot earlier and before the whole Lupo thing happened. I just feel that since I was the dev for that particular app (that happens to be important to the community) that I have some responsibilities that I didn't live up to.
Although, if Lupo was going to rip it off, it was going to happen regardless of the release status, so I guess that one was beyond my control. It's disappointing though.
Is this thread still going? Let it die people! Leave "loophole" to his (or her) devices.
Listen, and understand. That loophole is out there. He(she) can't be bargained with. He can't be reasoned with. He doesn't feel pity, or remorse, or fear. And he absolutely will not stop, ever, until PA.c is dead.
Pages