Printable View
Hum.. No he didn't gave up. He waiting someone code the RESTapi to he finish the Communication Engine.
I didn't finished the API in Swagger also, but we already have sufficient stuff in Swagger to do the basics of the Communication.
The developers of Yupi are afk, i think it's university stuff.
I'm also busy with university stuff.
But in my vacations will work hardly in Yupi.
im late
how can cms be "small" and "fast" by
-combing high end c extension with hard installation for newbies with heavy framework
also if you're going for "rest api" why not use lumen? the fastest framework designed for apis, same developer as laravel
also
cms plan is dumb and you're overcomplicating things, learn KISS
points 1 and 2 contradict
rest of points are basic features of most frameworks
1. Will be a small and fast CMS
2. Using Laravel or PhalconPHP as Framework
3. Composer compatible
4. Built-in Installer
5. Template Engine
6. PDO & MVC
7. REST Module
Your comment it's outdated @LeChris. See the discussions.
Those topics it's what i say to me when i want to go to sleep. Obviously will not be that.
As the developers said, Laravel supports Installer. I mean to create a Installer.
Small, it's small in disk space and size. Using SVG or SASS.
Thanks but i don't decide about the Framework. Know about kISS. Who will say what will be used it's @kylon
I only suggested Phalcon or Laravel, personally i hate PHP Frameworks. Prefer code my own algorithms and learn with it. Some cases using libraries to help.
Which point is contradicting with what?.... [......]
What you mean with..
"Comining High end C extension"..
Heavy Framework... Hum... as i said, i prefer no Framework, but i don't know if the knowledge of Kylon it's advanced sufficient for that. He is learning most PHP. Like you, in my opinion.
Also know about Lumen, good idea. Really fast and small.
Again @kylon will decide what will be done.
Those topics made by me, was an initial issue. Only to search about what can be merged in the software.
The internet has so many PHP frameworks that this is becoming to bore me.
So much same content. So much less innovation.
- - - Updated - - -
Observation.: KISSMVC it's outdated.
- - - Updated - - -
Observation.: Most thing that eat disk space are images and javascript.
CMS would be zero JavaScript. And zero Images.
No JS and no Images?
Welcome to 1999!
No Need of it.Quote:
Originally Posted by iExit
SVG and SASS Images does a quite good job.
Why using JavaScript? We don't will need that. Maybe only for the Housekeeping.
Obs.: Also Less can do that.
Quote:
Originally Posted by ovflowd
Well, I'm sure you know what you're talking about....Quote:
Originally Posted by ovflowd
You do not use SVG as a primary format for images on a website.Quote:
Originally Posted by ovflowd
It should only be used where suitable, personally I only use it for rendering vector art such as logos. Mainly when I'm doing mobile application development because it keeps it looking crispy on every device. It's not something that you should be using throughout a normal website because it will make your website slow. I'm not sure what you're planning to use it for but you shouldn't be using it at all specially considering this is a Habbo project which couldn't possible have a requirement for SVG at all. You're going to end up bloating the hell out of your website.
Always consider the user interface and the user's experience.Quote:
Originally Posted by ovflowd
You should only take a sacrifice on the user interface when it damages the user experience. If something takes a toll on performance or ruins/dictates the flow of an application that's when it comes an issue. Removing Javascript because you don't need it is a huge step to consider. Personally, I love when a website takes advantage of it. Single page applications are honestly going to be the future in user experience.
Please, oh please, do your research before starting a project.Quote:
Originally Posted by ovflowd
Please look into the concept of minification/optimization/compression. Corporations do not just launch a static nor dynamic website straight off the bat. They use various compression libraries and methods to ensure assets stored for the website remain at a minimum. Code should never launched off production in a beautified state. Some modern browsers even minify website's assets in realtime as whitespace nor trails are needed. Do not over do a technical process for the sake of it. J-Query only way weighs 241.59kb when compressed so I can not imagine you writing some Javascript code big enough to even hit the 1mb mark.
It's great that you're making observations and you're keen to learn. But always consider the disadvantages alongside the advantages of a technical process. Even HTML5 supports application caching alongside JavaScript but these really shouldn't be concerned unless you're developing some sort of fully pledged web application.
Research is key otherwise you'll end up with a spaghettified and bloated website.
Good luck, I'm still lurking around on the thread.
Okay,
I understand you're a horrible web developer, so I'll summarize.
KISS means to "Keep it simple, stupid"
Using a framework ,alongside an embedded and horribly implemented REST API to "be secure" is redundant, as any framework you use will automatically clean queries and any types of data used. Also, using any framework will more than triple your stack investment, and by the time you run composer installation it'll be 5 times the size of your assets (css/images).
Also,
There is plenty of innovation but a lot of people such as yourself are doing what has already been done, (re inventing the wheel) and considering it innovative because you're new to it. I have been using Laravel, Lumen, Angular, Node for a good year now and Sledmore is also using Laravel alongside an amazingly great javascript library for HabboRP. Using a framework isn't innovative, and not using a framework and creating your own algorithms is asking for bugs and issues (God forgiving I mention this, but your first PHP experience?)
Also, a few pointers to remember before doing a project of a high enough caliber
-Have an idea in mind
You currently have no clue what the fuck you're dealing with in terms of security, causing you to write ALL WEB LOGIC ON YOUR SERVER? It isn't a REST API just because it's following a REST method on a system not designed for it, and especially highly inefficient at that, nor is it secure. Using a framework would be more than a hundred times better in terms of security and efficiency.
-Talk to your team
You obviously have no clue if Kylon is even capable, and you're mentioning random frameworks around assuming it'll be easy for your users to setup. There is a reason most hotels use Rev and Plus. It isn't that it's good, it's because they're easy. using any framework is a PR suicide, and not using one is a Code fluency suicide.
Basically, learn more of how web development works
@Francis Joseph, i know all those things that you're saying. The onliest image in the CMS will be the logo, on max. It's a small CMS. With a minimal design. Really minimal design. With Client/Register/Index/Me/Staff/Articles.. And i think that's enough.
I'm not wondering about a complete suite for this project. Only a small thing, since Yupi works different.
I appreciate your big text Francis, your words are really more affordable than the words from LeChris, where he doesn't explain his point.
I know SVG isn't made for purpose of replacing Images of a web site, it's used for logos, art concepts, etc. Like as you said.
I know about codecs/compression, i'm doing Network Communications Engineering xD
You're right in all those points.
My user experience will be minimalist. I really don't know if a lot of users will use Yupi. And its development its really slowed down.
I agree that dynamic content is much better than static content.
Remember this is a test scenario. Yupi is in alpha. We don't are planning make something big yet. Not yet.
Thanks Francis!
you dislike my point because it's pointing out the flaws in your systemQuote:
Originally Posted by ovflowd
The system ever exists. How you can point flaws?Quote:
Originally Posted by LeChris
- - - Updated - - -
Sometimes i prefer say random things.Quote:
Originally Posted by Joopie
You know about REST? Than why are you using it on such a retarded scale, and not actually using frameworks in the ways intended and ways to be secure. End users don't trust Yupi because it's made by the developers of Azure, which was more cancerous than the Spanish Butterfly edits.
(Much love for Mikkel, on the other hand and the other main contributor to it)
Why? This makes you sound like a creep, just saying :P:
https://github.com/sant0ro/Yupi
http://i.imgur.com/DAUXtVD.png
It's to make fun. But you're right will change it.Quote:
Originally Posted by Quackster
- - - Updated - - -
@Quackster, updated it.
- - - Updated - - -
Answering to @iExit about JavaScript: You Might Not Need JavaScript
I'm sure we all can agree on you with the context of that article. Yet I think the title of that article is wrong and misleading.Quote:
Originally Posted by ovflowd
The reason I find this is because that JavaScript can do so much more then just, like that article is saying, do UI components. Yet I still believe that this isn't what @iExit was referring too. He was talking about "single page app/website/application". This is done by utilizing JavaScript. And there is so much that you couldn't do without JavaScript.