Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 09 2018 15:37
    nicksagona commented #4
  • Oct 09 2018 15:37
    nicksagona closed #4
  • Oct 08 2018 21:38
    adrix71 reopened #4
  • Oct 08 2018 21:38
    adrix71 closed #4
  • Oct 08 2018 21:34
    adrix71 commented #4
  • Oct 08 2018 21:27
    nicksagona commented #4
  • Oct 08 2018 21:27
    nicksagona commented #4
  • Oct 08 2018 21:27
    nicksagona commented #4
  • Oct 08 2018 21:19
    adrix71 opened #4
  • Oct 01 2018 16:04

    nicksagona on 3.2.3

    (compare)

  • Oct 01 2018 16:03

    nicksagona on master

    Add version proprety to module (compare)

  • Oct 01 2018 16:03

    nicksagona on v3-dev

    Add version proprety to module (compare)

  • Sep 14 2018 21:52
    eshell192007 starred popphp/popphp
  • Jul 07 2018 04:22
  • Jan 29 2018 22:22

    nicksagona on 3.2.2

    (compare)

  • Jan 29 2018 22:22

    nicksagona on 3.2.2

    (compare)

  • Jan 29 2018 22:21

    nicksagona on master

    Update license & copyright (compare)

  • Jan 29 2018 22:21

    nicksagona on v3-dev

    Update license & copyright (compare)

  • Jan 29 2018 21:05

    nicksagona on v2

    Update license (compare)

  • Jan 29 2018 18:22

    nicksagona on 3.2.2

    (compare)

Nick Sagona
@nicksagona
but all that said, you need to understand (and this might be my fault in how things are named)
Adriano Giovannini
@adrix71
So you're going in the direction of using everything for the composer.
Nick Sagona
@nicksagona
Pop is the application framework. Pop does have application modules that act as "mini applications" managed by the main application object.
Phire was written using Pop, but Phire's modules/plugins are not Pop modules, they are essentially plugins that are custom to the Phire eco-system and have to be installed via the Phire web UI (a la Wordpress)
that is what I'm leaning towards (doing everything with composer)
basically it's the debate of
A) Do you have a more developer-centric CMS that requires a dev to use the CLI and composer, etc?
or
B) Do you keep it more designer-friendly and have it all happen with the web UI via a custom module/plugin manager, etc?
personally I'm torn between the two options b/c I feel like either one could alienate the other audience, you know?
but seeing as I'd like to look into doing a more headless or decoupled CMS (with API support) I think option A might be better suited for that
(doing everything with composer, and also NPM/node as well)
Adriano Giovannini
@adrix71
I understand what you mean. The reality would like something not like WordPress, Joomla, Drupal etc. but something very much based on the use of CLI.
Nick Sagona
@nicksagona
so that's your preference as well? something that uses composer/CLI?
Adriano Giovannini
@adrix71

However, keep in mind that based on composer, npm etc., elephants are created.

Nova is a cms based on npm and composer that makes use of the CLI and is 128MB because of the thousands of libraries that are installed.

The Phire V4 App (the one based on bootstrap) is 70MB

There is no risk of having too many addictions that are useless and of the applications that take up a lot of space.

In my opinion the way of a CMS oriented as Phire v2 is still the most viable and the one that could bring the greatest advantages.

Without excluding the use of CLI.

Nick Sagona
@nicksagona
yea that's also been a goal of mine... I don't like apps that are unnecessarily bloated. I like skinny, streamlined and efficient.
Adriano Giovannini
@adrix71
Total agree

So (in my opinion) time and commitments allowing you could start with completing the cms v3 and then start correcting the modules that require it or writing more.

The alternative is to stop but it does not seem to be the case. Pop and Phire are two big pieces of code and I do not think it's worth stopping.

Nick Sagona
@nicksagona
Yea "time and commitments allowing" heh
that's the real trick isn't it heh
(just patched the docs issue)
Adriano Giovannini
@adrix71

Warning I use a lot of the translator so some things are misguided so it seemed you do everything yourself.

No, there are me too and also for me it is worth the time permitting.

Nick Sagona
@nicksagona
oh I understand... I'd love to have people help out... the reason I put Phire down for a bit was two reasons really... 1) After a few years of working on it, it didn't seem to get the traction I had hoped and 2) the new job I took on in 2016 required me to focus more on Pop and I didn't have the time (or need) to focus on Phire as much
and doing both Pop and Phire, I had always hoped to get other people involved using and contributing if others liked them
but that's been slow going as well...
but a few people pop in here and there to give a little bit of input, so that's nice
Adriano Giovannini
@adrix71

I discovered Phire and POP because I was looking for something that did not have dependencies and I immediately liked your work.

It happens that people appear who give a little input and offer to help you. The problem is that if they do not see results after a while they go away because one can study the libraries until they are memorized but nobody knows them as you have planned them and your contribution becomes fundamental if not fundamental.

Nick Sagona
@nicksagona
Well I usually answer and response to people's input or issues as fast as I can. There's been some good contributions that have helped a bit
Adriano Giovannini
@adrix71
I hope I continue and I hope to give you good ones too
Nick Sagona
@nicksagona
I appreciate that. I'm glad you like the work
Adriano Giovannini
@adrix71

While I'm talking about code work and I was seeing that in PhireCMS2 in src / Module.php on line 209 there is this loop (foreach ($ modules-> rows () like $ module) {) but the rows () method does not seem exist in version 4.3.0 of the database because I get a method error not found. I think we can replace it like this (foreach ($ modules as $ module)

What do you think about it?

Obviously I'm trying to port for version 3 to give you a hand.
Nick Sagona
@nicksagona
yea there's prob going to be some backwards compatibility issues like that
the pop-db component has been updated significantly over the past year
Adriano Giovannini
@adrix71
No problem on this. The problems are solved.
Nick Sagona
@nicksagona
so you are correct, ->rows() no longer exists b/c the object is a collection that is iterable itself
Adriano Giovannini
@adrix71
Will there be a src / Module.php file in the module structure in the future?
Nick Sagona
@nicksagona
most likely yes... that still holds true... that's the Pop application module that gets registered with the main application object
Adriano Giovannini
@adrix71
Very right
Adriano Giovannini
@adrix71
However I saw that at the time the modules can not be loaded because the tar and zip libraries are missing. You removed them.
Satisfy my curiosity. Is there anything in the form class that generates html markup? I do not think I saw it but I would like to be sure.
Nick Sagona
@nicksagona
yes the pop-archive repository was deprecated as unnecessary. Moving on from that, I just use the built-in Zip and Phar utilities now
well there's a whole pop-form repository that does the bulk of all the form work
renders HTML, validates fields, scrubs/filters data, etc etc
Adriano Giovannini
@adrix71
I got it
Adriano Giovannini
@adrix71
Good afternoon
Adriano Giovannini
@adrix71
Goo dafternoon
MOHD AFEEF
@afeef1915_twitter
im new in pops framwork can anyone give tutorial how to save data in mysql
i have understanding of symfony2,3 and laravel
Nick Sagona
@nicksagona
You can check out the docs here: http://docs.popphp.org/
Nick Sagona
@nicksagona
iamszt
@iamszt
i want to acheive the following
i have a predefined pdf file i want to add watermark or page number to each page
DrewM
@AndrewM
Curious if this has been addressed - I haven't been able to find any documentation or comments about it. When I get a record and modify, then ->save() it doesn't seem to trigger the 'ON UPDATE CURRENT_TIMESTAMP' for the database column....
It works fine with a normal db->query() though.