Hey Justin, first of all, congrats on creating this amazing component! 

To be honest I was creating my own templates, but honestly, your framework is so much more comprehensive and professional I might just use it instead :)

I am a bit of a noob in Outsystems and I couldn't find how to install the Demo. I downloaded it, however the OSP file doesn't seem to be recognized by Service Studio. What am I missing?

 I am using Service Studio 11.50 for MacOS - would that be the issue?

Thanks

Alex

Never mind, Justin, I was able to figure it out.

I uploaded the Solution in Service Center 

Thanks

Glad you figured it out, and happy you like the component!

J.Ja

Hi Adam,

I, like Justin are one of the OutSystems community moderators.

Even though the reply from Justin is deleted, and I guess by himself, I like to  share my opinion. 

Your passive aggressive / condescending reply about a best practice, touches a delicate subject, and could also have been subject for a moderator to reply.

Component creators put their spare free time in contribution to the community with great components. The Application Framework component built by Justin is one of the largest Forge components, that is still maintained by Justin, again... for free (next to all the great OutSystems articles he wrote).

Now I would not have chosen the same words as Justin, but I 100% agree with his message. Given the dislikes on yours and the likes on his reply, I don't stand alone.

-- Daniel

Hi Daniel, you try to approve the attitude of this guy?

No, as I said, I would not choose the same words, however I agree with the message.

Glad to hear that of you.  This guy's reactions were beyond believe and disconcerning.  

But my real point here is that this guy doesn't seem to be able to comply with the general OS basic best practice by doing at least some sort of documenting on a comprehensive Forge component. Which makes  to me the quality of this Forge component doubtful.

Adam, I think we talk in circles. 

'that guy' is still #8 in member ranking with huge ranking score on 40 created Forge components, and 38 OutSystems articles. This tells me that a large part of the community uses (and likes) the Forge components out there built by Justin.

Lets agree to disagree about whether Application Framework Forge component used by many community members has doubtful quality. May think different than you.

Feel free to contribute to the community by helping documenting Forge components ;)

Adam,  instead of wasting your time on this free component.. you should just spend the time to write your own.. which should only take about 2-3 months of effort and don’t forget to document it and share it for everyone to use for free.

- Paul

Who is censoring you Adam?, no reply of you has been moderator or removed. Instead the reply of Justin is deleted.  

Can you please explain me why you consider this weakness and a lack of openness?

Adam, you seem to read very selectively what you want to read in replies.

Yes, you are correct, documentation is missing, and it is a best practice to document code.
You are free to comment on that, nobody is disallowing you to do that. It doesn't mean some one didn't do a good job. I would say the best code doesn't even need documentation it documents itself.

This whole discussion is not triggered because of that but because:

• You try to make a point that the Forge creator is not doing something you feel he is obliged to do (which he isn't), we can debate if there should or not should be documentation, but the reality is he is not obliged to provide it.
• You try to make your point, in a Post not even created by you, where Justin actually took his spare time to help someone with question on the Application Framework Forge component.
• You conclude that because of the documentation the Forge component is hampered in its usage, you have the right to have that opionion, but doesn't make it a fact.
• You keep calling him 'that guy' and use write in a consending way ("It is with some embarrassment now that I need to point out")

Hello Adam,

We accept your criticism.
The matter is not what you are pointing out. It's the way you are pointing out.

The component lacks documentation and descriptions? Yes.

But instead of just pointing this out in a way that seems to be a "demand from you" (not nice) or an "obligation from the developer" (not true), maybe you could try to understand that the component is shared as it is, for free.

Justin (or any component developer), does not have the obligation of providing documentation / comments, and they may not be able to do this for a number of reasons.

We are all trying to help each other in the forum and through components we create (for fun, to learn, for necessity).

Being a bit more comprehensive over the limitations of time and so on when criticizing creates a much more friendly environment and boosts the willingness of people in trying to help you, when you need help.